chore(compose): enable --enable-schema-eviction in precompute quickstart - #44
Merged
Merged
Conversation
The quickstart precompute compose was missing `--enable-schema-eviction`, so Expired schemas (produced by a `StreamingConfig` swap that removed an agg_id, or by `POST /api/v1/db/schemas/:id/expire`) stayed resident in the registry forever and their data never got dropped from the store. The e2e that added retire/expire endpoints in #42 surfaced this: calling `force_expire` flipped the schema's status immediately but the data kept hanging around until a backend restart (which wipes the registry entirely — the opposite of what the §5 service is designed to manage). Also sets `--schema-eviction-poll-secs=60` (down from the 300s default) to make the eviction visible inside a demo run. Production deployments should raise this. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
docker-compose-precompute.ymlqueryengine service was missing--enable-schema-eviction, so Expired schemas (from aStreamingConfigswap that removed an agg_id, or from the newPOST /api/v1/db/schemas/:id/expirein #42) stayed resident forever and their data was never dropped from the store — the opposite of what the §5 eviction service is designed to do.What's in this PR
--enable-schema-evictionto the queryengine command indocker-compose-precompute.yml.--schema-eviction-poll-secs=60(down from 300s default) so the eviction is visible inside a demo run. Production deployments should raise this.Why
The e2e that added retire/expire endpoints in #42 called
force_expireand observed the schema flipped to Expired immediately — but the data kept hanging around until a backend restart (which wipes the whole registry, not what §5 intends).Test plan
docker compose -f docker-compose-precompute.yml -f docker-compose-precompute.local.yml up -dboots the queryengine cleanlyPOST /api/v1/db/schemas/:agg_id/expire, then wait ~60s, then verify:GET /api/v1/db/schemasno longer lists the agg_idGET /store/metrics🤖 Generated with Claude Code